Virtual printer interface node

ABSTRACT

A virtual printer interface node enables a non-cloud-ready printer to communicate with a cloud-based service, residing on an internet. The virtual printer interface node includes a housing; a communication interface to provide communication directly to the network router; and a microcontroller operatively connected to the communication interface. The microcontroller converts commands, received through the communication interface, from the cloud-based service, residing on the internet, to native protocols of the non-cloud-ready networked printer and communicates the converted native protocols to the non-cloud-ready networked printer.

BACKGROUND

Cloud computing is the use of computing resources (hardware andsoftware) that are delivered as a service over a network (typically theInternet). Traditionally, cloud computing has been focused onweb/cloud-based applications and web-connected mobile devices. However,as these web/cloud-based applications and mobile devices have becomemore capable, users expect the same capabilities from theseweb/cloud-based applications and mobile devices that the users receivefrom the users' personal computers. One such capability is printing.

Printing architectures and protocols (print drivers) of conventionalpersonal computer operating systems can be complex and many times areproprietary to the manufacturers of the printing device.

In contrast, a cloud based system is based upon achieving coherence andeconomies of scale, thereby relying upon converged infrastructure andshared services. Thus, the complexity and proprietary nature of theconventional printing architectures and protocols negatively impact thefeasibility of implementing a cloud-based printing service.

One solution has been the development of cloud-ready printers. Theseprinters have built-in systems (native support) for connecting to cloudprint services. A cloud-ready printer has no need for a personalcomputer connection of any kind or for a print driver. The printer canbe simply connected directly to a network and then registered with acloud print service to enable such a printer render print jobs.

However, this solution is not readily backward compatible with the vastnumber of existing conventional network printers that rely upon theconventional printing architectures and protocols. A network-readyprinter is a printer that includes a network interface (wired orwireless) that allows the printer to be directly connected to a network.

One conventional approach, as illustrated in FIG. 1, to enable aconventional network printer to be “cloud-ready” includes runningsoftware “connector” on a personal computer 20 associated with theconventional network printer 10, wherein the software “connector”registers the network printer, through a network 30, with thecloud-based service residing on the internet 40.

When a print job is submitted from the cloud-based service residing onthe internet 40 to the registered printer 10, the print job is actuallyrouted by the network 30 to the associated personal computer 20.

The communication channel 60 between the network 30 and the associatedpersonal computer 20 may be wired or wireless.

The software “connector,” running on the personal computer 20, submitsthe print job to the printer 10, through the network 30, using thepersonal computer operating system's native printer software.

The communication channel 50 between the network 30 and the printer 10may be wired or wireless.

The software “connector,” running on the personal computer 20, alsocommunicates, through the network 30, with the cloud-based printservice, residing on the internet 40, regarding any status informationassociated with the printer.

Although this approach provides the printer 10 with a “connection” to acloud-based service residing on the internet 40, the solution requiresthat the personal computer 20 remain powered ON, be executing thesoftware “connector,” and be connected to the network 30.

In other words, the conventional approach for enabling a non-cloud-readynetwork printer to be a cloud-ready printer is not a standalone solutionbut requires a personal computer in combination with the conventionalnon-cloud-ready network printer.

Thus, it is desirable to provide a device for a non-cloud-ready printer,which enables the printer to be cloud-ready.

Moreover, it is desirable to provide a device for a non-cloud-readyprinter, which enables the printer to be cloud-ready and does notrequire a personal computer to be running.

Furthermore, it is desirable to provide a plug-n-play inline device fora non-cloud-ready printer, which enables the printer to be a cloud-readyprinter.

In addition, it is desirable to provide a plug-n-play network device,which enables a non-cloud-ready printer to be a cloud-ready printer anddoes not require a personal computer to be running.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are only for purposes of illustrating various embodimentsand are not to be construed as limiting, wherein:

FIG. 1 illustrates a block diagram of a conventional system to enable aconventional network printer to be “cloud-ready;”

FIG. 2 illustrates a block diagram of system using an inline device toenable a conventional network printer to be “cloud-ready;”

FIG. 3 illustrates a block diagram of system using a network device toenable a conventional network printer to be “cloud-ready;”

FIG. 4 illustrates a block diagram of an inline virtual printerinterface node;

FIG. 5 illustrates a block diagram of a network virtual printerinterface node;

FIG. 6 illustrates a flowchart showing the generation of anauthentication code for the virtual printer interface node;

FIG. 7 illustrates a flowchart showing the authentication processbetween a virtual printer interface node and a cloud-based service; and

FIG. 8 illustrates a flowchart showing the identification of the propertranslation application to be utilized by the virtual printer interfacenode.

DETAILED DESCRIPTION

For a general understanding, reference is made to the drawings. In thedrawings, like references have been used throughout to designateidentical or equivalent elements. It is also noted that the drawings maynot have been drawn to scale and that certain regions may have beenpurposely drawn disproportionately so that the features and conceptscould be properly illustrated.

A cloud environment uses of computing resources (hardware and software)that are delivered as a service over a network (typically the Internet).For example, in a cloud environment, a user can “rent” applicationsoftware and/or databases, wherein the “cloud” providers manage theinfrastructure and platforms on which the applications run, and thedatabases are stored.

In another example, end users may access cloud-based applicationsthrough a web browser or a light-weight desktop or mobile app while thesoftware and user's data are stored on servers at a remote location.

As mentioned above, a user may desire to have a conventionalnon-cloud-ready printer be fully functional with cloud based services.To have a conventional non-cloud-ready printer be fully functional withcloud based services, the issues with the native protocols andarchitecture of the conventional non-cloud-ready printer not beingreadily compatible with the protocols of the cloud based service.

As illustrated in FIG. 2, an inline virtual printer interface node 25 isprovided to enable communication between a conventional non-cloud-readyprinter 10 and a cloud-based print service, residing on the internet 40.The inline virtual printer interface node 25 is connected between thenetwork (router) 30 and the conventional non-cloud-ready printer 10.

The communication channel 62 (connection) between the inline virtualprinter interface node 25 and the network (router) 30 may be wired orwireless.

It is further noted that the inline virtual printer interface node 25,if the communication channel 62 (connection) between the inline virtualprinter interface node 25 and the network (router) 30 is “wired,” mayinclude a cable jack port (RJ45) for receiving a cable coming from thenetwork (router) 30.

On the other hand, it is noted that the inline virtual printer interfacenode 25, if the communication channel 62 (connection) between the inlinevirtual printer interface node 25 and the network (router) 30 is“wired,” may include a cable jack for plugging in directly to a port ofthe network (router) 30.

Moreover, the communication channel 55 (connection) between the inlinevirtual printer interface node 25 and the conventional non-cloud-readyprinter 10 may be wired or wireless.

It is further noted that the inline virtual printer interface node 25,if the communication channel 55 (connection) between the inline virtualprinter interface node 25 and the conventional non-cloud-ready printer10 is “wired,” may include a cable jack port (RJ45) for receiving acable coming from the conventional non-cloud-ready printer 10.

On the other hand, it is noted that the inline virtual printer interfacenode 25, if the communication channel 55 (connection) between the inlinevirtual printer interface node 25 and the conventional non-cloud-readyprinter 10 is “wired,” may include a cable jack for plugging in directlyto a port (network interface) of the conventional non-cloud-readyprinter 10.

The inline virtual printer interface node 25 converts the nativeprotocols of the conventional non-cloud-ready printer 10 to a unifiedprotocol that can be used by a cloud based service, residing on theinternet 40. In addition, the inline virtual printer interface node 25converts the protocols used by the cloud based service, residing on theinternet 40, to the native protocols of the conventional non-cloud-readyprinter 10.

Since the inline virtual printer interface node 25 is a physical devicethat is inline between the conventional non-cloud-ready printer 10 andthe network (router) 30, the system does not require a personal computerto be running to enable the conventional non-cloud-ready printer 10 tobe “cloud-ready.”

In another embodiment, as illustrated in FIG. 3, a network virtualprinter interface node 35 is provided to enable communication between aconventional non-cloud-ready printer 10 and a cloud-based print service,residing on the internet 40. The network virtual printer interface node35 is connected to the network (router) 30 and communicates with theconventional non-cloud-ready printer 10 through the network (router) 30.

The communication channel 62 (connection) between the network virtualprinter interface node 35 and the network (router) 30 may be wired orwireless.

It is further noted that the network virtual printer interface node 35,if the communication channel 62 (connection) between the network virtualprinter interface node 35 and the network (router) 30 is “wired,” mayinclude a cable jack port (RJ45) for receiving a cable coming from thenetwork (router) 30.

On the other hand, it is noted that the network virtual printerinterface node 35, if the communication channel 62 (connection) betweenthe network virtual printer interface node 35 and the network (router)30 is “wired,” may include a cable jack for plugging in directly to aport of the network (router) 30.

Moreover, the communication channel 57 (connection) between the network(router) 30 and the conventional non-cloud-ready printer 10 may be wiredor wireless.

The network virtual printer interface node 35 converts the nativeprotocols of the conventional non-cloud-ready printer 10 to a unifiedprotocol that can be used by a cloud based service, residing on theinternet 40. In addition, the network virtual printer interface node 35converts the protocols used by the cloud based service, residing on theinternet 40, to the native protocols of the conventional non-cloud-readyprinter 10.

In this embodiment, the network virtual printer interface node 35receives commands from the cloud based service, residing on the internet40, through the network (router) 30, and converts these commands to thenative protocols of the conventional non-cloud-ready printer 10. Thenetwork virtual printer interface node 35 then communicates theconverted native protocols to the conventional non-cloud-ready printer10, through the network (router) 30.

In addition, the network virtual printer interface node 35 may receiveinformation from the conventional non-cloud-ready printer 10, throughthe network (router) 30, and convert this information into a form thatcan be readily processed by the cloud based service, residing on theinternet 40. The network virtual printer interface node 35 thencommunicates the converted information to the cloud based service,residing on the internet 40, through the network (router) 30.

Since the network virtual printer interface node 35 is a physical devicethat is in communication with the conventional non-cloud-ready printer10 and the network (router) 30, the system does not require a personalcomputer to be running to enable the conventional non-cloud-readyprinter 10 to be “cloud-ready.”

FIG. 4 illustrates a block diagram of an inline virtual printerinterface node 250. The inline virtual printer interface node 250includes a housing 251, two communication interfaces, 253 and 259, amicrocontroller or processor 255, and a memory 257.

The communication interfaces, 253 and 259, enable a communicationchannel to be established between the inline virtual printer interfacenode 250 and a conventional non-cloud-ready printer or a network(router).

For example, communication interface 253 may enable a communicationchannel to be established between the inline virtual printer interfacenode 250 and a conventional non-cloud-ready printer, and communicationinterface 253 may enable a communication channel to be establishedbetween the inline virtual printer interface node 250 and a network(router).

If the communication channel enabled by the communication interface 253is wireless, the communication interface 253 would include a transmitterand receiver capable of providing wireless communication.

If the communication channel enabled by the communication interface 259is wireless, the communication interface 259 would include a transmitterand receiver capable of providing wireless communication.

If the communication channel enabled by the communication interface 253is wired, the communication interface 253 may include a cable jack port(RJ45) for receiving a cable.

For example, if the communication channel enabled by the communicationinterface 253 is a wired communication channel between the conventionalnon-cloud-ready printer and the inline virtual printer interface node250, the communication interface 253 would include a cable jack port(RJ45) for receiving a cable coming from the conventionalnon-cloud-ready printer.

If the communication channel enabled by the communication interface 259is wired, the communication interface 259 may include a cable jack port(RJ45) for receiving a cable.

For example, if the communication channel enabled by the communicationinterface 259 is a wired communication channel between the conventionalnon-cloud-ready printer and the inline virtual printer interface node250, the communication interface 259 would include a cable jack port(RJ45) for receiving a cable coming from the conventionalnon-cloud-ready printer.

If the communication channel enabled by the communication interface 253is wired, the communication interface 253 may include a cable jack forplugging in directly to a port of a network interface.

For example, if the communication channel enabled by the communicationinterface 253 is a wired communication channel between the conventionalnon-cloud-ready printer and the inline virtual printer interface node250, the communication interface 253 would include an integral cablejack that would plug directly into the cable jack port (RJ45) on theconventional non-cloud-ready printer.

If the communication channel enabled by the communication interface 259is wired, the communication interface 259 may include a cable jack forplugging in directly to a port of a network interface.

For example, if the communication channel enabled by the communicationinterface 259 is a wired communication channel between the conventionalnon-cloud-ready printer and the inline virtual printer interface node250, the communication interface 259 would include an integral cablejack that would plug directly into the cable jack port (RJ45) on theconventional non-cloud-ready printer.

The microcontroller or processor 255, in conjunction with memory 257,converts commands from a cloud based service, residing on the internet,received through one of the communication interfaces (253 or 259), tothe native protocols of a conventional non-cloud-ready printer. Themicrocontroller or processor 255 then causes the converted nativeprotocols to be communicated to the conventional non-cloud-ready printerthrough the other communication interfaces (253 or 259).

The microcontroller or processor 255, in conjunction with memory 257,also converts information from a conventional non-cloud-ready printer,received through one of the communication interfaces (253 or 259), intoa form that can be readily processed by the cloud based service,residing on the internet. The microcontroller or processor 255 thencauses the converted information to be communicated to the cloud basedservice, residing on the internet, through the other communicationinterfaces (253 or 259).

It is noted that the microcontroller or processor 255 and memory 257 maybe realized by an application specific integrated circuit (ASIC).

It is also noted that the memory 257 may have pre-stored the informationand commands necessary to convert the commands from a cloud basedservice, residing on the internet, to the native protocols of a specificconventional non-cloud-ready printer.

Moreover, it is noted that the inline virtual printer interface node 250may include functionality to identify the make and model of theconventional non-cloud-ready printer connected thereto. Based upon theidentity the make and model of the conventional non-cloud-ready printerconnected to the inline virtual printer interface node 250, the inlinevirtual printer interface node 250 could download, from the internet,the information and commands necessary to convert the commands from acloud based service, residing on the internet, to the native protocolsof the identified conventional non-cloud-ready printer.

FIG. 5 illustrates a block diagram of a network virtual printerinterface node 350.

The network virtual printer interface node 350 includes a housing 351, acommunication interface 359, a microcontroller or processor 355, and amemory 357.

The communication interface 359 enables a communication channel to beestablished between the network virtual printer interface node 350 and aconventional non-cloud-ready printer or a network (router).

For example, communication interface 359 may enable a communicationchannel to be established between the network virtual printer interfacenode 350 and a conventional non-cloud-ready printer, and communicationinterface 359 may enable a communication channel to be establishedbetween the network virtual printer interface node 350 and a network(router).

If the communication channel enabled by the communication interface 359is wireless, the communication interface 359 would include a transmitterand receiver capable of providing wireless communication.

If the communication channel enabled by the communication interface 359is wired, the communication interface 359 may include a cable jack port(RJ45) for receiving a cable.

For example, if the communication channel enabled by the communicationinterface 359 is a wired communication channel between the conventionalnon-cloud-ready printer and the network virtual printer interface node350, the communication interface 359 would include a cable jack port(RJ45) for receiving a cable coming from the conventionalnon-cloud-ready printer.

If the communication channel enabled by the communication interface 359is wired, the communication interface 359 may include a cable jack forplugging in directly to a port of a network interface.

For example, if the communication channel enabled by the communicationinterface 359 is a wired communication channel between the conventionalnon-cloud-ready printer and the network virtual printer interface node350, the communication interface 359 would include an integral cablejack that would plug directly into the cable jack port (RJ45) on theconventional non-cloud-ready printer.

The microcontroller or processor 355, in conjunction with memory 357,converts commands from a cloud based service, residing on the internet,received through the communication interface 359, to the nativeprotocols of a conventional non-cloud-ready printer. The microcontrolleror processor 255 then causes the converted native protocols to becommunicated to the conventional non-cloud-ready printer through thecommunication interface 359.

The microcontroller or processor 355, in conjunction with memory 357,also converts information from a conventional non-cloud-ready printer,received through the communication interface 359, into a form that canbe readily processed by the cloud based service, residing on theinternet. The microcontroller or processor 355 then causes the convertedinformation to be communicated to the cloud based service, residing onthe internet, through the communication interface 359.

It is noted that the microcontroller or processor 355 and memory 357 maybe realized by an application specific integrated circuit (ASIC).

It is also noted that the memory 357 may have pre-stored the informationand commands necessary to convert the commands from a cloud basedservice, residing on the internet, to the native protocols of a specificconventional non-cloud-ready printer.

Moreover, it is noted that the network virtual printer interface node350 may include functionality to identify the make and model of theconventional non-cloud-ready printer connected thereto. Based upon theidentity the make and model of the conventional non-cloud-ready printerconnected to the network virtual printer interface node 350, the networkvirtual printer interface node 350 could download, from the internet,the information and commands necessary to convert the commands from acloud based service, residing on the internet, to the native protocolsof the identified conventional non-cloud-ready printer.

It is noted that since the network virtual printer interface node 350 isnot inline with the conventional non-cloud-ready printer, the networkvirtual printer interface node 350 may be located (connected to)anywhere on the local area network.

It is noted that the virtual printer interface node can receive powerover the cables connected to the communication interfaces. If thecommunication interfaces are wireless, the virtual printer interfacenode would receive power from a power source.

It is noted that although the virtual printer interface node has beendescribed with respect to a conventional non-cloud-ready printer, thevirtual printer interface node can be utilized with a conventionalnon-cloud-ready multifunction printer; i.e., a device having at leastscanning, printing, and copying functionality.

It is further noted that although the virtual printer interface node hasbeen described with respect to a conventional non-cloud-ready printer,the virtual printer interface node can be utilized with a networkstand-alone scanner. In this situation, the virtual printer interfacenode converts the commands from a cloud based service, residing on theinternet, to the native protocols of scanner.

The virtual printer interface node enables a conventionalnon-cloud-ready printer to be availed of cloud-based control basedservices. These services that are based on acquiring data from theconventional non-cloud-ready printer as well as sending commands to theconventional non-cloud-ready printer.

For example, these services may include break-fix service contracts,supplies contracts, remote monitoring services, and other related printservices.

To enable these services, the microcontroller of the virtual printerinterface node provides the mechanism to translate between various localarea network (LAN) side protocols; such as simple network managementprotocol (SNMP), hypertext transfer protocol (HTTP), hypertext transferprotocol secure (HTTPs), exchange web service (EWS) screen scraping; andwide area network (WAN) or cloud side protocols; such as customerpremise equipment wan management protocol (CWMP) being used as atransport protocol with command set being (a derivative of) theTechnical Report 069 (TR 069) specification set.

The microcontroller of the virtual printer interface node may alsoprovide the mechanism to translate between the native applicationprogramming interface of the conventional non-cloud-ready printer andthe application programming interface of the cloud based service. Inthis situation, the virtual printer interface node acts a proxy betweenthe conventional non-cloud-ready printer and an application thatcommunicates using a different interface platform by providing either auniversal application programming interface on the WAN side or cloudside of the virtual printer interface node or enabling the communicationwith various interface platforms, wherein the memory would store thenecessary information and instructions to recognize the interface beingused by the application attempting to access the conventionalnon-cloud-ready printer and provide the proper translation to the nativeapplication programming interface of the conventional non-cloud-readyprinter.

The microcontroller of the virtual printer interface node would alsoprovide the translation of the native application programming interfaceof the conventional non-cloud-ready printer to the applicationprogramming interface of the cloud-based application that theconventional non-cloud-ready printer is attempting to access.

For example, a third party provider may offer an application whichcommunicates via the interface platform of the third party interfaceplatform. The virtual printer interface node would act as a proxy toallow the third party application to communicate with a non-enabledthird party interface platform device (conventional non-cloud-readyprinter) having a different application programming interface.

The microcontroller of the virtual printer interface node may alsoprovide the mechanism to translate between local area network basedprotocols for the conventional non-cloud-ready printer to firewallfriendly wide area network based protocols so as to allow theconventional non-cloud-ready printer to be able to connect to externalservices (cloud based services).

In the various situations described above, the virtual printer interfacenode would need the appropriate translation application (translationprogram and/or translation driver) to enable communication therebetween.

As illustrated in FIG. 8, the virtual printer interface node, at stepS810, determines the identity of the device to which it will act as atranslator (proxy) and the cloud-based service being utilized.

With respect to the determination the identity of a printing device towhich it will act as a translator (proxy), the virtual printer interfacenode may identify the print driver for the printing device, or thevirtual printer interface node may identify the application programminginterface utilized by the printing device.

If the device was a scanner, the virtual printer interface node mayidentify the driver for the scanner, or the virtual printer interfacenode may identify the application programming interface utilized by thescanner.

With respect to the determination the identity of the cloud-basedservice being utilized, the virtual printer interface node may identifythe application programming interface utilized by the cloud-basedservice.

This identification process enables the virtual printer interface nodeto identify the translation couplet.

The virtual printer interface node, at step S820, determines if theappropriate translation application for the identified translationcouplet is stored on the virtual printer interface node.

If the appropriate translation application for the identifiedtranslation couplet is stored on the virtual printer interface node, atstep S840, the appropriate stored translation application is retrievedfrom a memory in the virtual printer interface node.

If the appropriate translation application for the identifiedtranslation couplet is not stored on the virtual printer interface node,at step S830, the appropriate translation application is downloaded fromthe internet; i.e., downloaded from a website (server) associated withthe manufacture of the virtual printer interface node.

The acquired appropriate translation application is executed, as stepS850.

The microcontroller of the virtual printer interface node can execute aweb server application to provide administration, interaction,reporting, and control from a user's browser which is connected throughthe local area network or proxied through the cloud connection forremote device interaction. In the later situation, the virtual printerinterface node, as noted above, would provide the necessary translationsbetween the native protocols and native application programminginterface of the conventional non-cloud-ready printer and the cloudbased service.

The virtual printer interface node also enables a conventionalnon-cloud-ready multifunction printer to be availed of cloud-basedcontent based services. These services are based on moving documents toand from conventional non-cloud-ready multifunction printer to the cloudservices such as a cloud service bridge

The cloud service bridge is a universal gateway to cloud based thirdparty services. The virtual printer interface node implements a specialcloud service bridge client that facilitates the document interchangeprocesses between the conventional non-cloud-ready multifunction printerand the cloud service bridge, which in turn may pass some or all thedocument to a third party service for additional processing. Suchcontent based services may include: workflow automation, contentconversion such as print-ready conversion, optical characterrecognition, etc.

The content based services could also include consumer services such asbrokering and optimization of content that may be available on thebroadcast TV or other internet based news channels, feeds, images orother content.

Various examples of content based cloud services are described inco-pending U.S. patent application Ser. No. 13/673,733, filed on Nov. 9,2012, and entitled “NETWORKED PRINTING SYSTEMS.” The entire content ofco-pending U.S. patent application Ser. No. 13/673,733 is herebyincorporated by reference.

The virtual printer interface node further enables a conventionalnon-cloud-ready printer to be availed of device networking services.These services enable conventional non-cloud-ready printer, through thevirtual printer interface node, to join a network of other devices thatcan be exposed to various communities. These communities can be part ofa social network, for example, and once exposed to the conventionalnon-cloud-ready printer, can utilize the services from the conventionalnon-cloud-ready printer.

For example, the virtual printer interface node can enable theconventional non-cloud-ready printer to be connected to a social networksuch that when content is uploaded to the community, the content can bereadily or automatically printed by the virtual printer interface node.

These communities can also exist for the purpose of enabling anecommerce model to charge for the service of using the conventionalnon-cloud-ready printer once the conventional non-cloud-ready printer isexposed to the community.

As noted above, conventional non-cloud-ready printers utilize differentversions of an application programming interface making it difficult fora third party system provider to invest adequately in learning aprogramming system that has a limited applicability, thereby limitingthe benefits the third party system provider can provided for theconventional non-cloud-ready printer. The virtual printer interface nodeimplements a universal application programming interface protocolconverter such that the third party only needs to invest in a singleprogramming language and interface.

As noted above, since the virtual printer interface node enables theconventional non-cloud-ready printer to be availed of cloud basedservices, the virtual printer interface node can be used to gateservices for the conventional non-cloud-ready printer.

For example, if the conventional non-cloud-ready printer is amultifunction printer (having printing, copying, and/or scanningfunctionality), the virtual printer interface node could be used to gateservices in the MFP based on a subscription model.

In this scenario, the virtual printer interface node acts to block usageof the multifunction printer, through content intercept or passing ofsettings to the multifunction printer to enable or disable certainfeatures. If a valid active subscription is confirmed, the virtualprinter interface node would enable those features.

For security purposes, the virtual printer interface node can utilizeauthentication protocols to prevent a misuse of remote services.

An authentication process is illustrated in FIG. 6. As illustrated inFIG. 6, the virtual printer interface node, at step S610, determines theidentity of the device to which it is connected.

If the virtual printer interface node is an inline virtual printerinterface node for a printing device, the virtual printer interface nodewould identify the printing device.

On the other hand, if the virtual printer interface node is a networkvirtual printer interface node, the virtual printer interface node wouldidentify the router for the local area network.

The virtual printer interface node, at step S620, also determines itsidentity.

At step S630, the virtual printer interface node creates anauthentication code based upon the identity of the device to which it isconnected and its identity. This would enable the authentication code tobe linked or tied to the device/virtual printer interface node pair.

It is also noted that the authentication code could be generated using apassword or other mechanism that uniquely identifies the authorized userof the virtual printer interface node. In this instance, the virtualprinter interface node can be utilized with various devices by theauthorized user.

At step S640, the generated authentication code is registered with thecloud-based service.

It is noted that the generated authentication code may be registeredwith a cloud-based service associated with the virtual printer interfacenode so that if the proper authentication code is not received by thecloud-based service associated with the virtual printer interface node,the virtual printer interface node is blocked from being utilized.

If the virtual printer interface node is blocked from being utilized,this state of operation would not prevent the connected device frombeing used under normal conditions. In other words, the communicationswould pass through the virtual printer interface node without processingor translation.

As illustrated in FIG. 7, when the virtual printer interface node isinvoked, at step S710, the cloud-based service associated with thevirtual printer interface node requests an authentication code, at stepS720. The virtual printer interface node, at step S730, generates anauthentication code in a similar manner as described above with respectto FIG. 6.

The authentication code, at step S740, is transmitted to the cloud-basedservice associated with the virtual printer interface node, and thecloud-based service associated with the virtual printer interface nodevalidates, at step S750, the received authentication code.

If the received authentication code is valid, the cloud-based serviceassociated with the virtual printer interface node may transmit anactivation code to the virtual printer interface node to allow thevirtual printer interface node to be utilized. The activation code couldbe time based in that the activation period of the virtual printerinterface node may be defined in the activation code; i.e., activationfor thirty minutes.

If the received authentication code is not valid, the cloud-basedservice associated with the virtual printer interface node may transmita deactivation code to the virtual printer interface node to block thevirtual printer interface node from being utilized.

In the alternative, if the received authentication code is not valid,the cloud-based service associated with the virtual printer interfacenode would not transmit an activation code. In this situation, thevirtual printer interface node would be designed not to be activated(functional) without the proper activation code.

For example, the virtual printer interface node may, when the virtualprinter interface node is connected to a conventional non-cloud-readyprinter, poll the conventional non-cloud-ready printer to obtain uniqueidentification of the conventional non-cloud-ready printer; such as themedia access control (MAC) address of the conventional non-cloud-readyprinter.

The virtual printer interface node may combine this identificationinformation with the identification information; such the media accesscontrol (MAC) address, of the virtual printer interface node to create aunique authentication code.

This unique identification code may be registered with the cloud basedservice associated with the virtual printer interface node such thatwhenever a cloud based service is accessed that requires thefunctionality of the virtual printer interface node, the cloud basedservice associated with the virtual printer interface node would requestthe authentication code.

If the virtual printer interface node is connected to a differentprinter than when the authentication code was registered with the cloudbased service associated with the virtual printer interface node and theauthentication code is based upon the device/virtual printer interfacenode pair, the authentication code generated by the virtual printerinterface node would be different from the registered code because thecode would be a combination of the identification of the new printer andthe identification of the virtual printer interface node. In such asituation, the cloud based service would block utilization of thevirtual printer interface node.

However, as noted above, the printer could still be utilized in thelocal area network environment.

More specifically, each time the virtual printer interface node needs tocommunicate with a cloud based service; the virtual printer interfacenode would create an authentication code based on current conventionalnon-cloud-ready printer connected thereto. This tying of theauthentication code to the identification of both the virtual printerinterface node and the conventional non-cloud-ready printer prevents thevirtual printer interface node from being improperly used with anotherunauthorized printer.

On the other hand, if the authentication code is a user/virtual printerinterface node pair, whenever the cloud based service associated withthe virtual printer interface node requests the authentication code, thevirtual printer interface node would have to acquire the useridentification mechanism and generate the authentication code therefrom.The user identification mechanism may be acquired through a userinterface on the connected device or other input mechanism.

In summary, the virtual printer interface node intercepts communicationsbetween the cloud-based service and the conventional non-cloud-readyprinter and provides the appropriate conversion so that the cloud-basedservice and the conventional non-cloud-ready printer can effectivelycommunicated therebetween.

An inline virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a first communication interface to provide communicationdirectly to the network router; a second communication interface toprovide communication directly to the non-cloud-ready networked printer;and a microcontroller operatively connected between the firstcommunication interface and the second communication interface. Themicrocontroller converts commands, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.The microcontroller communicates, through the second communicationinterface, the converted native protocols to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and aninline virtual printer interface node. The inline virtual printerinterface node includes a housing; a first communication interface toprovide communication directly to the network router; a secondcommunication interface to provide communication directly to thenon-cloud-ready networked printer; and a microcontroller operativelyconnected between the first communication interface and the secondcommunication interface. The microcontroller converts commands, receivedthrough the first communication interface, from the cloud-based service,residing on the internet, to native protocols of the non-cloud-readynetworked printer. The microcontroller communicates, through the secondcommunication interface, the converted native protocols to thenon-cloud-ready networked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The non-cloud-ready networked printer may include scanning, copying, andprinting functionality.

A network virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router includes ahousing; a communication interface to provide communication directly tothe network router; and a microcontroller operatively connected to thecommunication interface.

The microcontroller converts commands, received through thecommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the communication interface,the converted native protocols to the non-cloud-ready networked printer.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface m a transmitter/receiver to create awireless communication channel with the network router.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printerincludes a non-cloud-ready networked printer; a network router; and anetwork virtual printer interface node. The network virtual printerinterface node includes a housing; a communication interface to providecommunication directly to the network router; and a microcontrolleroperatively connected to the communication interface. Themicrocontroller converts commands, received through the communicationinterface, from the cloud-based service, residing on the internet, tonative protocols of the non-cloud-ready networked printer. Themicrocontroller communicates, through the communication interface, theconverted native protocols to the non-cloud-ready networked printer.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface m a transmitter/receiver to create awireless communication channel with the network router.

The non-cloud-ready networked printer may include scanning, copying, andprinting functionality.

An inline virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router includes ahousing; a first communication interface to provide communicationdirectly to the network router; a second communication interface toprovide communication directly to the non-cloud-ready networked printer;and a microcontroller operatively connected between said firstcommunication interface and said second communication interface.

The microcontroller converts commands, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the second communicationinterface, the converted native protocols to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and aninline virtual printer interface node. The inline virtual printerinterface node includes a housing, a first communication interface toprovide communication directly to the network router, a secondcommunication interface to provide communication directly to thenon-cloud-ready networked printer, and a microcontroller operativelyconnected between the first communication interface and the secondcommunication interface.

The microcontroller converts commands, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the second communicationinterface, the converted native protocols to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A network virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a communication interface to provide communication directlyto the network router; and a microcontroller operatively connected tothe communication interface.

The microcontroller converts commands, received through thecommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the communication interface,the converted native protocols to the non-cloud-ready networked printer.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and anetwork virtual printer interface node.

The network virtual printer interface node includes a housing; acommunication interface to provide communication directly to the networkrouter; and a microcontroller operatively connected to the communicationinterface.

The microcontroller converts commands, received through thecommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the communication interface,the converted native protocols to the non-cloud-ready networked printer.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

An inline virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a first communication interface to provide communicationdirectly to the network router; a second communication interface toprovide communication directly to the non-cloud-ready networked printer;and a microcontroller operatively connected between the firstcommunication interface and the second communication interface.

The microcontroller converts commands associated with a firstapplication programming interface language, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to commands associated with a native application programminginterface language of the non-cloud-ready networked printer, the firstapplication programming interface language being different from thenative application programming interface language of the non-cloud-readynetworked printer.

The microcontroller communicates, through the second communicationinterface, the converted commands associated with the native applicationprogramming interface language of the non-cloud-ready networked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and aninline virtual printer interface node.

The inline virtual printer interface node includes a housing, a firstcommunication interface to provide communication directly to the networkrouter, a second communication interface to provide communicationdirectly to the non-cloud-ready networked printer, and a microcontrolleroperatively connected between the first communication interface and thesecond communication interface.

The microcontroller converts commands associated with a firstapplication programming interface language, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to commands associated with a native application programminginterface language of the non-cloud-ready networked printer, the firstapplication programming interface language being different from thenative application programming interface language of the non-cloud-readynetworked printer.

The microcontroller communicates, through the second communicationinterface, the converted commands associated with the native applicationprogramming interface language of the non-cloud-ready networked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A network virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a communication interface to provide communication directlyto the network router; and a microcontroller operatively connected tothe communication interface.

The microcontroller converts commands associated with a firstapplication programming interface language, received through thecommunication interface, from the cloud-based service, residing on theinternet, to commands associated with a native application programminginterface language of the non-cloud-ready networked printer, the firstapplication programming interface language being different from thenative application programming interface language of the non-cloud-readynetworked printer.

The microcontroller communicates, through the communication interface,the converted commands associated with the native applicationprogramming interface language of the non-cloud-ready networked printer.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and anetwork virtual printer interface node.

The network virtual printer interface node includes a housing; acommunication interface to provide communication directly to the networkrouter; and a microcontroller operatively connected to the communicationinterface.

The microcontroller converts commands associated with a firstapplication programming interface language, received through thecommunication interface, from the cloud-based service, residing on theinternet, to commands associated with a native application programminginterface language of the non-cloud-ready networked printer, the firstapplication programming interface language being different from thenative application programming interface language of the non-cloud-readynetworked printer.

The microcontroller communicates, through the communication interface,the converted commands associated with the native applicationprogramming interface language of the non-cloud-ready networked printer.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

An inline virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a first communication interface to provide communicationdirectly to the network router; a second communication interface toprovide communication directly to the non-cloud-ready networked printer;and a microcontroller operatively connected between the firstcommunication interface and the second communication interface.

The microcontroller converts local area network based protocols receivedfrom the conventional non-cloud-ready printer to firewall friendly widearea network based protocols, the firewall friendly wide area networkbased protocols enabling the conventional non-cloud-ready printer to beable to connect to the cloud-based service.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and aninline virtual printer interface node.

The inline virtual printer interface node includes a housing; a firstcommunication interface to provide communication directly to the networkrouter; a second communication interface to provide communicationdirectly to the non-cloud-ready networked printer; and a microcontrolleroperatively connected between the first communication interface and thesecond communication interface.

The microcontroller converts local area network based protocols receivedfrom the conventional non-cloud-ready printer to firewall friendly widearea network based protocols, the firewall friendly wide area networkbased protocols enabling the conventional non-cloud-ready printer to beable to connect to the cloud-based service.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A network virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a communication interface to provide communication directlyto the network router; and a microcontroller operatively connected tothe communication interface.

The microcontroller converts local area network based protocols receivedfrom the conventional non-cloud-ready printer to firewall friendly widearea network based protocols, the firewall friendly wide area networkbased protocols enabling the conventional non-cloud-ready printer to beable to connect to the cloud-based service.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes anon-cloud-ready networked printer; a network router; and anetwork virtual printer interface node.

The network virtual printer interface node includes a housing; acommunication interface to provide communication directly to the networkrouter; and a microcontroller operatively connected to the communicationinterface.

The microcontroller converts local area network based protocols receivedfrom the conventional non-cloud-ready printer to firewall friendly widearea network based protocols, the firewall friendly wide area networkbased protocols enabling the conventional non-cloud-ready printer to beable to connect to the cloud-based service.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

An inline virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a first communication interface to provide communicationdirectly to the network router; a second communication interface toprovide communication directly to the non-cloud-ready networked printer;and a microcontroller operatively connected between the firstcommunication interface and the second communication interface.

The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and aninline virtual printer interface node.

The inline virtual printer interface node includes a housing; a firstcommunication interface to provide communication directly to the networkrouter; a second communication interface to provide communicationdirectly to the non-cloud-ready networked printer; and a microcontrolleroperatively connected between the first communication interface and thesecond communication interface.

The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

A network virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a communication interface to provide communication directlyto the network router; and a microcontroller operatively connected tothe communication interface.

The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and anetwork virtual printer interface node.

The network virtual printer interface node includes a housing; acommunication interface to provide communication directly to the networkrouter; and a microcontroller operatively connected to the communicationinterface.

The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

An inline virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a first communication interface to provide communicationdirectly to the network router; a second communication interface toprovide communication directly to the non-cloud-ready networked printer;and a microcontroller operatively connected between the firstcommunication interface and the second communication interface.

The microcontroller converts commands, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the second communicationinterface, the converted native protocols to the non-cloud-readynetworked printer.

The microcontroller converts commands associated with a firstapplication programming interface language, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to commands associated with a native application programminginterface language of the non-cloud-ready networked printer, the firstapplication programming interface language being different from thenative application programming interface language of the non-cloud-readynetworked printer.

The microcontroller communicates, through the second communicationinterface, the converted commands associated with the native applicationprogramming interface language of the non-cloud-ready networked printer.The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and aninline virtual printer interface node.

The inline virtual printer interface node includes a housing; a firstcommunication interface to provide communication directly to the networkrouter; a second communication interface to provide communicationdirectly to the non-cloud-ready networked printer; and a microcontrolleroperatively connected between the first communication interface and thesecond communication interface.

The microcontroller converts commands, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the second communicationinterface, the converted native protocols to the non-cloud-readynetworked printer.

The microcontroller converts commands associated with a firstapplication programming interface language, received through the firstcommunication interface, from the cloud-based service, residing on theinternet, to commands associated with a native application programminginterface language of the non-cloud-ready networked printer, the firstapplication programming interface language being different from thenative application programming interface language of the non-cloud-readynetworked printer.

The microcontroller communicates, through the second communicationinterface, the converted commands associated with the native applicationprogramming interface language of the non-cloud-ready networked printer.The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a port to receive a second cable connected to the non-cloud-readynetworked printer.

The first communication interface may be a port to receive a first cableconnected to the network router and the second communication interfacemay be a jack for plugging into a network port of the non-cloud-readynetworked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a port to receive a second cableconnected to the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router and thesecond communication interface may be a jack for plugging into a networkport of the non-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a port to receive a second cable connected to thenon-cloud-ready networked printer.

The first communication interface may be a jack for plugging into anetwork port of the network router and the second communicationinterface may be a transmitter/receiver to create a wirelesscommunication channel with the non-cloud-ready networked printer.

The first communication interface may be a transmitter/receiver tocreate a wireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote device interaction

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

A network virtual printer interface node for providing communicationbetween a cloud-based service, residing on an internet, and anon-cloud-ready networked printer through to a network router, includesa housing; a communication interface to provide communication directlyto the network router; and a microcontroller operatively connected tothe communication interface.

The microcontroller converts commands, received through thecommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the communication interface,the converted native protocols to the non-cloud-ready networked printer.

The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

A system for providing communication between a cloud-based service,residing on an internet, and a non-cloud-ready networked printer,includes a non-cloud-ready networked printer; a network router; and anetwork virtual printer interface node.

The network virtual printer interface node includes a housing; acommunication interface to provide communication directly to the networkrouter; and a microcontroller operatively connected to the communicationinterface.

The microcontroller converts commands, received through thecommunication interface, from the cloud-based service, residing on theinternet, to native protocols of the non-cloud-ready networked printer.

The microcontroller communicates, through the communication interface,the converted native protocols to the non-cloud-ready networked printer.

The microcontroller polls the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller creates an authentication code based on theidentification information retrieved from the non-cloud-ready networkedprinter and identification information associated with thenon-cloud-ready networked printer associated with the inline virtualprinter interface node.

The microcontroller registers the created authentication code with thecloud-based service.

The communication interface may be a port to receive a first cableconnected to the network router.

The communication interface may be a jack for plugging into a networkport of the network router.

The communication interface may be a transmitter/receiver to create awireless communication channel with the network router.

The microcontroller may execute a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.

The microcontroller may gate services provided by the non-cloud-readynetworked printer in response to restrictions communicated from thecloud-based service to the non-cloud-ready networked printer.

The identification information associated with the non-cloud-readynetworked printer may be a media access control address.

The identification information associated with the inline virtualprinter interface node may be a media access control address.

The microcontroller may poll, in response to an authentication requestform the cloud based-service, the non-cloud-ready networked printer toretrieve identification information associated with the non-cloud-readynetworked printer.

The microcontroller may create an authentication code based on theauthentication request triggered identification information retrievedfrom the non-cloud-ready networked printer and identificationinformation associated with the non-cloud-ready networked printerassociated with the inline virtual printer interface node.

It will be appreciated that various of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be desirablycombined into many other different systems or applications. Also thatvarious presently unforeseen or unanticipated alternatives,modifications, variations or improvements therein may be subsequentlymade by those skilled in the art which are also intended to beencompassed by the following claims.

What is claimed is:
 1. An inline virtual printer interface node forproviding communication between a cloud-based service, residing on aninternet, and a non-cloud-ready networked printer through to a networkrouter, comprising: a housing; a first communication interface toprovide communication directly to the network router; a secondcommunication interface to provide communication directly to thenon-cloud-ready networked printer; and a microcontroller operativelyconnected between said first communication interface and said secondcommunication interface; said microcontroller converting commands,received through said first communication interface, from thecloud-based service, residing on the internet, to native protocols ofthe non-cloud-ready networked printer; said microcontrollercommunicating, through said second communication interface, theconverted native protocols to the non-cloud-ready networked printer. 2.The inline virtual printer interface node as claimed in claim 1, whereinsaid first communication interface is a port to receive a first cableconnected to the network router and said second communication interfaceis a port to receive a second cable connected to the non-cloud-readynetworked printer.
 3. The inline virtual printer interface node asclaimed in claim 1, wherein said first communication interface is a portto receive a first cable connected to the network router and said secondcommunication interface is a jack for plugging into a network port ofthe non-cloud-ready networked printer.
 4. The inline virtual printerinterface node as claimed in claim 1, wherein said first communicationinterface is a transmitter/receiver to create a wireless communicationchannel with the network router and said second communication interfaceis a port to receive a second cable connected to the non-cloud-readynetworked printer.
 5. The inline virtual printer interface node asclaimed in claim 1, wherein said first communication interface is atransmitter/receiver to create a wireless communication channel with thenetwork router and said second communication interface is a jack forplugging into a network port of the non-cloud-ready networked printer.6. The inline virtual printer interface node as claimed in claim 1,wherein said first communication interface is a jack for plugging into anetwork port of the network router and said second communicationinterface is a port to receive a second cable connected to thenon-cloud-ready networked printer.
 7. The inline virtual printerinterface node as claimed in claim 1, wherein said first communicationinterface is a jack for plugging into a network port of the networkrouter and said second communication interface is a transmitter/receiverto create a wireless communication channel with the non-cloud-readynetworked printer.
 8. The inline virtual printer interface node asclaimed in claim 1, wherein said first communication interface is atransmitter/receiver to create a wireless communication channel with thenetwork router.
 9. The inline virtual printer interface node as claimedin claim 1, wherein said microcontroller executes a web serverapplication to provide administration, interaction, reporting, andcontrol from a browser which is proxied through the cloud-based servicefor remote device interaction.
 10. The inline virtual printer interfacenode as claimed in claim 1, wherein said microcontroller gates servicesprovided by the non-cloud-ready networked printer in response torestrictions communicated from the cloud-based service to thenon-cloud-ready networked printer.
 11. A system for providingcommunication between a cloud-based service, residing on an internet,and a non-cloud-ready networked printer, comprising: a non-cloud-readynetworked printer; a network router; and an inline virtual printerinterface node; said inline virtual printer interface node including, ahousing, a first communication interface to provide communicationdirectly to said network router, a second communication interface toprovide communication directly to said non-cloud-ready networkedprinter, and a microcontroller operatively connected between said firstcommunication interface and said second communication interface; saidmicrocontroller converting commands, received through said firstcommunication interface, from the cloud-based service, residing on theinternet, to native protocols of said non-cloud-ready networked printer;said microcontroller communicating, through said second communicationinterface, the converted native protocols to said non-cloud-readynetworked printer.
 12. The system as claimed in claim 11, wherein saidfirst communication interface is a port to receive a first cableconnected to said network router and said second communication interfaceis a port to receive a second cable connected to said non-cloud-readynetworked printer.
 13. The system as claimed in claim 11, wherein saidfirst communication interface is a port to receive a first cableconnected to said network router and said second communication interfaceis a jack for plugging into a network port of said non-cloud-readynetworked printer.
 14. The system as claimed in claim 11, wherein saidfirst communication interface is a transmitter/receiver to create awireless communication channel with said network router and said secondcommunication interface is a port to receive a second cable connected tosaid non-cloud-ready networked printer.
 15. The system as claimed inclaim 11, wherein said first communication interface is atransmitter/receiver to create a wireless communication channel withsaid network router and said second communication interface is a jackfor plugging into a network port of said non-cloud-ready networkedprinter.
 16. The system as claimed in claim 11, wherein said firstcommunication interface is a jack for plugging into a network port ofsaid network router and said second communication interface is a port toreceive a second cable connected to said non-cloud-ready networkedprinter.
 17. The system as claimed in claim 11, wherein said firstcommunication interface is a jack for plugging into a network port ofsaid network router and said second communication interface is atransmitter/receiver to create a wireless communication channel withsaid non-cloud-ready networked printer.
 18. The system as claimed inclaim 11, wherein said first communication interface is atransmitter/receiver to create a wireless communication channel withsaid network router.
 19. The system as claimed in claim 11, wherein saidnon-cloud-ready networked printer includes scanning, copying, andprinting functionality.
 20. The system as claimed in claim 11, whereinsaid microcontroller executes a web server application to provideadministration, interaction, reporting, and control from a browser whichis proxied through the cloud-based service for remote deviceinteraction.
 21. The system as claimed in claim 11, wherein saidmicrocontroller gates services provided by the non-cloud-ready networkedprinter in response to restrictions communicated from the cloud-basedservice to the non-cloud-ready networked printer.